-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: handle exceeding maximum inputs when funding a transaction #2822
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mvares Nice work on this 👍 and thanks again for helping us.
I've left some suggestions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mvares We also need to implement a test case for this
I'm working on this. How could we simulate more than 250 inputs? |
Aditionally, the tests of CI are falling after the changes. cc @Torres-ssf |
TY, @Torres-ssf! Currently, I'm considering to mock |
b31faeb
to
6e2337d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mvares is this ready for review?
Co-authored-by: Peter Smith <peter@blueoceancomputing.co.uk>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
⛵
Release notes
In this release, we:
Summary
Enforces a maximum limit of 255 inputs for
funding
a transaction. If this limit isexceeded
, anerror
is triggered to prevent processing.Checklist
tests
to prove my changesdocs